home *** CD-ROM | disk | FTP | other *** search
-
-
-
-
-
-
- README.DOC
-
- This file contains details of the latest changes to the
- program and solutions to common problems encountered when
- running BIBLOGIC.
-
- It also contains instructions on installing BIBLOGIC.
-
-
-
-
- WHAT'S NEW
-
- Version 3.02 differs from Version 3.01 *ONLY* in the
- documentation & installation procedures. This release
- contains an updated README.DOC (containing help with
- run-time errors & with Windows 3.1), and FILE_ID.DIZ &
- WHATSNEW.302 have been added.
-
- The bulletin board .ZIP files have been merged into a single
- file to correct problems with distribution of partial
- packages.
-
- The Version number and copyright dates on the program itself
- have been updated to 3.02 for consistency.
-
-
-
-
- INSTALLATION OF BIBLOGIC VERSION 3.02
-
- BIBLOGIC is distributed in three forms:
-
- DISTRIBUTION DISKS. The program package is supplied on
- one or two floppy disks, depending on disk format. The
- files may be compressed, depending on your disk vendor.
-
- BULLETIN BOARD FILE. The program is supplied in the
- form of a compressed file (usually a .ZIP file, but
- some BBSs use other compression techniques).
-
- CD-ROM. The program is supplied as a subdirectory
- "\BIBLO302" containing uncompressed files. A compressed
- version is also included for BBS operators.
- NOTE: THE DEMO/TUTORIAL PROGRAM CAN BE RUN DIRECTLY
- FROM THE CD-ROM. CHANGE DIRECTORY TO THE BIBLO302
- SUBDIRECTORY ON THE CDROM AND TYPE: "DEMO<Enter>".
-
- In all cases, installation is similar. The instructions
- below assume that you have a basic working knowledge of DOS.
- If not, enlist the help of a friend or colleague with this
- process.
-
-
-
-
-
-
-
- 1) If you already have a copy of BIBLOGIC on your system,
- do NOT follow these instructions. See "UPDATING FROM A
- PREVIOUS VERSION..." below.
-
- 2) Log onto the hard disk where you intend to install
- BIBLOGIC by typing (for example):
-
- C:<Enter>
-
- 3) Change directory to the root directory by typing:
-
- CD \<Enter>
-
- 4) Make a new directory for BIBLOGIC, and change to that
- directory, by typing:
-
- MD BIBLOGIC<Enter>
- CD BIBLOGIC<Enter>
-
- NOTE: You MUST refer to the manual if you intend to
- install BIBLOGIC in a directory with a name other than
- \BIBLOGIC.
-
- 5) Now, copy or uncompress all of the BIBLOGIC files from
- the distribution disks, CD-ROM, or downloaded file. The
- procedure will vary depending on your source.
-
- You can check that your package is complete by
- comparing the directory against the list of files in
- PACKING.LST.
-
- 6) Check that the CONFIG.SYS file on your boot drive has
- at least FILES=20 and BUFFERS=15. If the values are
- higher, leave them at their current values because
- another program may require them to be higher. Be
- aware, however, that very high FILES and BUFFERS values
- use up a lot of memory and could stop BIBLOGIC from
- running.
-
- 7) If your CONFIG.SYS file contains a line activating
- EMM386.EXE, and you experience difficulties running
- BIBLOGIC, see the notes below regarding "Not enough
- memory" errors.
-
- 8) Remember to reboot your system if you changed your
- CONFIG.SYS.
-
- 9) Change directory to the new BIBLOGIC directory and run
- the demo/tutorial program by typing (for example):
-
- C:<Enter>
- CD \BIBLOGIC<Enter>
- DEMO<Enter>
-
-
-
-
-
-
-
- Running the demo is highly recommended, since it gives
- you an overview of how BIBLOGIC works.
-
-
-
-
- UPDATING FROM A PREVIOUS VERSION OF BIBLOGIC
-
- If you have Version 3.01, you do not need to update to
- Version 3.02. The reason for this minor release was to
- provide the information regarding error messages in this
- document (README.DOC).
-
- If you are updating from a previous version, you need only
- the following files:
-
- DEMO.BAT
- BIBLOGIC.DBD
- *.DOC
- *.EXE
- *.OVL
- Any new .PFF files you wish to use.
-
- The easiest way to update the system is to install the new
- system in a temporary directory (other than where the old
- system is installed) and then copy over the files you need.
-
- It is strongly recommended that you make a complete backup
- of your existing BIBLOGIC installation before attempting to
- update to the latest version.
-
- It is recommended that you run the demo program included in
- the distribution package. After updating, go to the new
- BIBLOGIC directory and type DEMO<Enter>.
-
-
-
-
- MANUALS
-
- MANUAL.DOC contains the BIBLOGIC instruction manual.
- SUPPL.DOC contains a supplement to the manual.
- README.DOC is this file.
- LICENSE.DOC contains the software license details.
- REGISTER.DOC contains a registration "form".
- VENDOR.DOC contains details for Disk Vendors and BBS
- operators.
-
-
- All of these files are in raw ASCII form and may be printed
- on any ASCII printer with 80 or more columns and 66 or more
- lines per page. The files contain form-feed characters
- between pages and use back-space characters for underlining
- and bold.
-
-
-
-
-
-
-
- To print these files, copy them directly to your ASCII
- printer or use the DOS print utility. For example:
-
-
- COPY *.DOC LPT1:
- or
- PRINT *.DOC
-
-
-
-
- RUNNING BIBLOGIC UNDER MICROSOFT WINDOWS 3.1
-
- Although BIBLOGIC is not a Windows application, it can be
- run under Windows 3.1. This allows you to switch back and
- forth between BIBLOGIC and your word-processor (or other
- applications). You can even do other things while BIBLOGIC
- makes reference lists in the background. To run BIBLOGIC
- under Windows 3.1, you must make a PIF file with the
- following parameters:
-
-
- Program Filename: BIBLOGIC.EXE
- Window Title: Biblogic 3.02
- Optional Parameters:
- Start-up Directory: C:\BIBLOGIC
-
- Video Memory: [X] Text [ ] Low Graphics [ ] High Graphics
-
- Memory Requirements: KB Required 440 KB Desired 640
- EMS Memory: KB Required 0 KB Limit 0
- XMS Memory: KB Required 0 KB Limit 0
-
- Display Usage: [ ] Full Screen Execution: [X] Background
- [X] Windowed
-
- [X] Close Window on Exit
-
-
- Open _DEFAULT.PIF and Save As BIBLOGIC.PIF after making the
- above changes. You may need to experiment a little with the
- 440 value for your particular system.
-
-
-
-
- "NOT ENOUGH MEMORY" ERROR
-
- If you get a "Not enough memory" error immediately after
- invoking BIBLOGIC at the DOS prompt, Check your CONFIG.SYS
- file for a line enabling EMM386.EXE. If the "NOEMS" option
- is specified, then "NOVCPI" must also be specified. Remember
- to reboot your computer if you make changes to CONFIG.SYS.
-
-
-
-
-
-
-
- The above change should allow BIBLOGIC to run correctly.
- Alternative solutions are: (1) Remove both "NOEMS" and
- "NOVCPI" options, (2) Do not invoke EMM386.EXE, or (3) Run
- BIBLOGIC under Windows 3.1 (see above)
-
-
-
-
- MISCELLANEOUS ERRORS, ESPECIALLY WHEN CREATING LISTS
-
- If BIBLOGIC runs out of conventional memory, the error
- message generated will usually refer to some file oriented
- activity (for example "Cannot open file XXXXXXXX.XXX").
-
- This most commonly occurs when creating a reference list
- (BIBLOGIC's most memory intensive task). To solve this
- problem, more conventional (640k) memory must be freed up.
- This can be done in several ways: (1) Remove unnecessary TSR
- programs (for example "pop-up" utilities from your
- AUTOEXEC.BAT file, (2) Remove unnecessary drivers from your
- CONFIG.SYS file, (3) Reduce your FILES and BUFFERS values in
- your CONFIG.SYS file (but not less than FILES=20 and
- BUFFERS=15), or (4) Run under Windows 3.1 instead of DOS.
-
- Error messages, especially errors described as "DOS Error",
- occurring during initialization (just after the program is
- invoked) are usually caused by insufficient FILES and/or
- BUFFERS values. Check that your CONFIG.SYS has at least
- FILES=20 and BUFFERS=15 and reboot your computer if you make
- changes.
-
-
-
-
- NOTICE
-
- This program is produced by a member of the Association of
- Shareware Professionals (ASP). ASP wants to make sure that
- the shareware principle works for you. If you are unable to
- resolve a shareware-related problem with an ASP member by
- contacting the member directly, ASP may be able to help. The
- ASP Ombudsman can help you resolve a dispute or problem with
- an ASP member, but does not provide technical support for
- members' products. Please write to the ASP Ombudsman at 545
- Grover Road, Muskegon, MI 49442 or send a CompuServe message
- via CompuServe Mail to ASP Ombudsman 70007,3536.
-
-
-
-
-
-
-
-
-
-
- ADDRESS
-
- Biblogic Computer Services can be contacted at:
-
- Biblogic Computer Services
- P.O. Box 1424
- Thousand Oaks
- CA 91358-0424
- U.S.A.
-
- Fax: +1 (805) 493-0364
- CompuServe: 75020,556
- E-mail: 75020.556@compuserve.com
-
- PLEASE NOTE: WE ARE UNABLE TO PROVIDE TELEPHONE SUPPORT.
-
-
-
-
- This file contains details of the latest changes to the program
- and solutions to common problems encountered when running
- BIBLOGIC.
-
- It also contains instructions on installing BIBLOGIC.
-